Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/sdk-readme.yml:
- Around line 6-25: Update the path filters in .github/workflows/sdk-readme.yml
so the workflow actually triggers when Node SDK sources change: add the Node
package paths (for example include 'sdk/packages/node/iii/src/**' and
'sdk/packages/node/iii/README.md' or broader 'sdk/packages/node/**') to both the
push and pull_request path lists so the guard step that probes
sdk/packages/node/iii/README.md and sdk/README.md runs when Node API-source
files are modified.
- Around line 84-89: The workflow step invoking check_python_readme.py is
incorrectly being run against the Node README (sdk/packages/node/iii/README.md),
which is a no-op because check_python_readme.py parses Python fenced blocks;
remove sdk/packages/node/iii/README.md from the arguments to the
check_python_readme.py invocation OR add a separate Node-specific guard:
create/run a Node/TS checker (e.g., check_node_readme.js or a tsc/ts-node
type-check command) against sdk/packages/node/iii/README.md and update the
workflow step to call that checker instead of passing the Node README into
check_python_readme.py.

In `@scripts/readme-guard/check_python_readme.py`:
- Around line 68-73: The parser currently swallows SyntaxError by returning []
after ast.parse(source) fails; change this so a SyntaxError in README Python
fences is treated as a test failure — raise or append a descriptive error
(include the snippet context) instead of returning an empty list in the
try/except around ast.parse in the function that parses fences; additionally,
wrap the calls to attr_calls_on_iii_var inside check_file (the block around the
lines currently invoking attr_calls_on_iii_var) in a try/except that catches
SyntaxError and reports it (rather than skipping), so malformed Python snippets
are reported as errors with clear context.

In `@sdk/packages/python/iii/CHANGELOG.md`:
- Around line 25-30: The changelog entry uses camelCase method names; update it
to Python-style snake_case: replace `call`, `callVoid`, `triggerVoid` with
`call`, `call_void`, `trigger_void` in the Removed section and ensure the usage
example references `iii.trigger()` and the Python `TriggerAction.Void()`
invocation; adjust the text so Python developers will see the correct snake_case
symbols (`call`, `call_void`, `trigger_void`, `trigger`, `TriggerAction.Void`)
when searching the codebase.

In `@sdk/packages/rust/iii/README.md`:
- Line 87: Examples use dotted function IDs; update them to use :: namespace
separators for consistency. Locate calls to iii.register_function and uses of
RegisterFunction::new_async (e.g., RegisterFunction::new_async("orders.create",
...)) and change string IDs from "orders.create" style to "orders::create" (and
any other dotted IDs in the README examples) so they match the :: convention
used elsewhere (e.g., stream::set/stream::update).

In `@sdk/README.md`:
- Around line 111-112: Update the cross-SDK API table to reflect that Python's
trigger() is synchronous (remove the leading "await" in the Python column for
the Invoke rows) and change any "Node/Python" example that currently uses JS
object literal syntax to use Python dict syntax instead (e.g., use
{"function_id": ..., "payload": ...} style for Python rather than JS object
notation); specifically edit the entries referencing iii.trigger(),
TriggerAction.Void(), and TriggerRequest examples so Python examples omit await
and use Python dicts where Node/Python is indicated.

---

Outside diff comments:
In `@sdk/packages/python/iii/README.md`:
- Around line 25-48: Update the example to perform a fire-and-forget trigger and
then cleanly stop the worker: call trigger with action=TriggerAction.Void() (or
equivalent) for the fire-and-forget invocation and then call iii.shutdown() at
the end to stop the background event-loop thread created by register_worker;
ensure the example imports/uses TriggerAction and demonstrates the shutdown call
after the trigger so a copy-pasted script will not hang.

---

Nitpick comments:
In `@sdk/packages/rust/iii/src/error.rs`:
- Around line 8-14: Change the NotConnected unit variant in the Error enum in
error.rs to carry the engine address (e.g., NotConnected(String)) and update its
Display/#[error(...)] message to interpolate that address instead of the
hardcoded default; then update all construction sites that create NotConnected
(references in iii.rs at the two locations and the three sites in channels.rs)
to pass the actual address String, and adjust the ergonomics test in
tests/ergonomics.rs to assert the new field or updated message accordingly.